-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Radius Custom Templates #16
Conversation
🎉 Now we can use our Radius custom templates for a scaffolded controller and action views. A project using this will still need to have `slim-rails` in it's own Gemfile since we are not monkey-patching any generators. However, because of that, we need to work around how the generators work. By default, rails will look for a template, and generate that first one it finds. Since our custom templates are in a gem, rails will find a template (default) in the project and spit it out. We want to check `radius-rails` first for any templates before going back to the defaults. Those changes are in `lib/radius-rails.rb`.
.panel-heading | ||
| My <%= plural_table_name.titleize %> | ||
|
||
table.table.table-hover.table-generic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to move the .table-generic
and any related styling over too.
@cupakromer Okay I think this is ready to merge and has all the basics for controller and view files. We are using |
I jumped the gun a bit on this PR - still WIP
Now we can use our Radius custom templates for a scaffolded controller and action views. A project using this will still need to have
slim-rails
in it's ownGemfile
since we are not monkey-patching any generators. However, because of that, we need to tweak and work around the generators behavior.By default, rails will look for a template, and generate that first one it finds. Since our custom templates are in a gem, rails will find a template (default) in the project and spit it out. We want to check
radius-rails
first for any templates before going back to the defaults. Those changes are inlib/radius-rails.rb
. I found that answer here.I remember I had an issue with a datetimepicker that wasn't resolved in an early version of
2.0.0
so I bumped the version.